home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Belgian Amiga Club - ADF Collection
/
BS1 part 23.zip
/
BS1 part 23
/
Master Virus Killer v2.1.adf
/
Master_Virus_Killer_v2.1
/
MVK.DOC
< prev
next >
Wrap
Text File
|
1991-03-11
|
29KB
|
671 lines
D O C U M E N T A T I O N
-------------------------
The M A S T E R V I R U S K I L L E R * *
* *
** 2.1
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
V1.0 ->1.4 Artwork and design: David Delabassée , Gaëtan Prouvost , X.Juste
V1.0 ->2.1 + Programming and (c): Xavier Leclercq
V2.0+ English Text Editing: Ed Kroes, Delft, The Netherlands
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
MVK2.1 Rights Reserved by Stefan Ossowski in GERMANY , AUSTRIA and
SWITZERLAND. For these countries the program is NOT Public Domain/Share Ware.
French Version 2.1 is not a Public Domain.
->FOR ALL OTHERS countries (BELGIUM , U.K. , USA ...) this program (ENGLISH
VERSION ONLY) IS PUBLIC DOMAIN (Share Ware). If you discover NEW viruses
please contact me :
Leclercq Xavier
Vieux Chemin D'Ath N°12 7548 WARCHIN BELGIUM
---------------------------------------------------------------------------
I am very interested in all viruses that are not covered by MVK and which
should therefore be included in future versions. Thanks in advance for
sending me such new viruses! YOU MAKE UPDATING POSSIBLE!
---------------------------------------------------------------------------
To obtain the list of key assignments:
Hold down the 'HELP' Key in the program.
IMPORTANT:
This documentation is on the disk and to print it :
1> type Master_Virus_Killer_V2.1/MVK.DOC to PRT:
1.List of viruses recognized by MVK v2.1:
-----------------------------------------
Bootblock Viruses & LINK :
--------------------------
001. (C)rackRight by Diskdoctors
002. 16 Bit Crew
003. 2001
004. Abraham (Class Abraham = MCA)
005. Aids
006. AmigaFreak
007. ASS Virus
008. Australian Parasite
009. BamigaSectorOne
010. BandVirusSlayer
011. BGS9 I [ LINK ]
012. BGS9 Mutant [ LINK ]
013. BlackFlash
014. BlackStar (North StarI)
015. Blade Runner
016. Butonic's = Bahan
017. ByteBandit I
ByteBandit II
018. ByteBanditClone
019. ByteBanditNoHead (ByteBandit v3 = ByteBandit+ = The Mutation)
020. CancerSmily by Centurions [ LINK ]
021. CCCP Virus (BOOT)
CCCP Virus [ Link ]
022. Clist = UK Style
023. Clonk
024. Coder
025. Dag
026. Dasa = Byte Warrior = DasaI = DasaII
027. Destructor
028. DigitalEmotion
029. Disaster Master [ LINK ]
030. Diskguard
031. DiskHerpes = Phantastograph = Phantasmumble = Herpes =....
032. Extreme
033. F.A.S.T.
034. F.I.C.A.
035. FastLoadByteWarrior
036. Forpib
037. Gadaffi
038. Graffiti
039. Gremlins (The True)
040. GXteam
041. Gyros
042. HCS 4220 I
043. HCS II
044. Hilly
045. Hoden
046. Ice
047. Incognito
048. IRQ typeI [ LINK ]
049. IRQ typeII [ LINK ]
050. Jeff Butonic V1.31 [ LINK ]
051. Jeff Butonic V3.00 [ LINK ]
052. Jitr
053. Joshua I
054. Joshua II = Switch OFF Virus
055. Julie = Tick
056. Kauki
057. LamerExterminator I (LamerStrap , LamerSpecial)
058. LamerExterminator II (Gremlins The False)
059. LamerExterminator III
060. LamerExterminator IV (SelwriterLamer)
061. LamerExterminator V
062. LamerExterminator VI (Rene Lamer6)
063. LamerExterminator VII
064. LamerExterminator VIII
065. LSD!
066. MAD II
067. MegaMaster (= MGM virus)
068. MicroMaster&AEK
069. MicroSystem
070. Morbid Angel
071. Newbeat (Alien Newbeat)
072. NoName
073. NorthStarII (starfire)
074. NorthStarIII
075. Obelisk 1
076. OPapa
077. Paramount
078. Paratax I
079. Paratax II
080. Pentagon Circle Virus Slayer I
081. Pentagon Circle Virus Slayer II
082. Pentagon Circle Virus Slayer III
083. RETURN OF LAMER EXTERMINATOR (R.o.l.e) !!!! [ Disk-Validator Virus ]
084. Revenge
085. Revenge of the Lamer Exterminator I [ LINK ]
086. Revenge of the Lamer Exterminator II [ LINK ]
087. RevengeLoader
088. SCA 1 (Uses move.l to copy itself in memory)
SCA 2 (Uses DoIO to copy itself in memory)
089. SCA-AIDS
090. ScarFace
091. Sendarian
092. SinisterSyndicate
Sinmut
093. Suntronic
094. SuperBoy
095. SupplyTeam
096. System Z PVL v3.0
097. System Z PVL v4.0
098. System Z PVL v5.0
099. System Z PVL v5.1
100. System Z PVL v5.3
101. System Z PVL v5.4
102. System Z PVL v6.1
103. System Z PVL v6.3
104. System Z PVL v6.4
105. System Z PVL v6.5
106. Target
107. Telstar (false System Z PVL v6.0)
108. Termigator
109. Terrorists [ LINK ]
110. The Ripper
111. The Time Bomber (Troyan Horse)
112. The Traveling Jack I [ LINK ] [*]
113. The Traveling Jack II [ LINK ] [*]
114. TimeBomb
115. Tomates-Gentechnic-Service
116. Turk
117. UltraFox
UltraKill
118. Virus II by Obelisk (very like Obelisk1!)
119. Virus-killer-Virus
120. Vkill I
Vkill II
122. Warhawk
123. Warsaw
124. XENO [ LINK ]
V2.0+ -> RETURN OF LAMER EXTERMINATOR located by the test of memory.
A new virus generation has been signalled:
Diskvalidator Viruses.
V2.1 -> The first of this new generation is "Return Of The Lamer". I will
deal with it in the version 2.1 of MVK : USE "R.O.L.E ?" ICON !
----------------------
Remarks:
--------
[ * ] Traveling Jack test is wrong ? I am not sure. Jack virus changes
his hunk length every copy... I hope fixed it in next MVK version...
-NBv2.1: Garrison, Judy , ABC and DoubleDensity BB are not Viruses..
-Kauki, Sinistersyndicate, SupplyTeam, ByteWarriorLoader, SystemZ, ASS
are not really Viruses but cause similar effects:
Screen handling manipulations, memory manipulations, alert displays
and most important: "hanging" your computer for many ROM versions!
In particular, SystemZ installs itself on the bootblock replacing the
standard block.
-The BGS9 is sometimes called the TTV1 Virus. If you want to understand
the reason, then look at the end of this document...
-Don't confuse the TERMIGATOR Virus with the Terminator protector!
-The IRQ Team, Termigator, Dasa, GxTeam, (C)rackright by Diskdoctors,
Alien Newbeat and Microsystems Viruses don't work under v1.3 ROM!
-All File Viruses (Link Viruses) are now fought by MVK2.1. Use the
"File Virus?" icon!
-NBv2.1: Garrison, Judy , ABC and DoubleDensity BB are not Viruses..
2.List of special bootblocks recognized by MVK2.1:
--------------------------------------------------
001. A-Max KickEnable
002. Amiga Army
003. Avirex Boot
004. Blizzard1.0 Protector
005. Boot Girl
006. Boot memory controller v1.2
007. Boot memory controller v1.3
008. Boot Pal
009. BootBlock COPY
010. BootBlock Generation
011. Bootblock OK...
012. BootLeg v2.1
013. Borderless
014. CCS-Boot
015. CHIP-Boot
016. Devil Blue Sky Checker
017. DevWare 88 BootBlock Protector
018. Doesn't Boot....
019. GX.TEAM NoFast
020. Interferon Checker
021. IRQ Protector v2.0
022. IRQ Protector [all versions]
023. M.i.A Boot
024. Mahomey&Kaktus Checker
025. Mega Boot v1.30
026. Noll's Checker
027. North Star Virus Checker
028. Outlaw Checker
029. Peetermans Koen MemChecker
030. Peter Stuar BB
031. Punisher BB
032. Pvl sound
033. RattleHead Boot
034. Razor1911 Checker
035. Red Antivirus
036. SCA protector Boot
037. Scoopex NTSC_PAL
038. SuperFly v2.0
039. Terminator Virus Protector
040. Thor V1.0
041. Tristar VirusKiller v1.1 Boot
042. Virus Detector Cleaner (VDC) v1.0
043. Virus Detector Cleaner (VDC) v1.1
044. Virus Detector Cleaner (VDC) v1.2
045. Virus Detector Cleaner (VDC) v1.3
046. Virus Detector Cleaner (VDC) v1.4
047. Virus Detector Cleaner (VDC) v1.5
048. Virus Detector Cleaner (VDC) v1.6
049. Virus Detector Cleaner (VDC) v1.7
050. Virus Detector Cleaner (VDC) v1.8
051. Virus Detector Cleaner (VDC) v1.9
052. Virus Detector Cleaner (VDC) v2.0
053. Virus Detector Cleaner (VDC) v2.1
054. Virus FREE BootBlock
055. Viruskiller Buster v1.4 Boot
056. VirusKiller Prof. v2.0 Boot
057. X-Copy v2.0 Bootblock
-The VDC and the IRQ Protector blocks can be installed by MVK:
The first one allows suppression during booting of no matter which virus
before going on to batch files (e.g. the startup-sequence).
The second one gives protection against the IRQ link virus which attaches
itself to executable files. The boot lets believe the virus that it is
already present in memory.
3.Information about the use of special keys:
--------------------------------------------
'F4' KEY: New option MVK2.0. Explanation: A virus may damage the boot
°°°°°°°°° of your hard disk destroying partition parameters. (Result=
NOT A DOS DISK and you must reformat the HD).I can help you if you meet
such a situation. First, use the 'C' Key to put the boot of your HD in the
buffer.
Second, SAVE the buffer, i.e. strike the 'F4' Key and SAVE the HD boot on a
target disk. (Never insert a disk before because this action will cause the
boot of this disk to be loaded as the new buffer!) Then:
'F3' KEY: New option MVK2.0. After problems with viruses destroying your
°°°°°°°°° HD boot, insert the disk with your old HD boot definition (see
above) and strike the 'F3' Key to make the buffer of this disk (old HD boot)
the new boot of your HD. This action will restore your hard disk.
NOTE
----
USE THE F3-F4 KEYS WITH CAUTION BECAUSE IF YOU INSTALL AN INAPPROPRIATE
BOOT YOUR HARDDRIVE WILL BE INCAPACITATED! ONLY for clever users!
(No insult intended.)
The HD boot checksum is not situated in the second long word as disk checksum
and if you change these 4 bytes (if you install a different boot) the HD
will not boot again! In this case use the workbench format command!
This note holds for the A590 and all other HD's!
'F1' KEY:
°°°°°°°°°
(Update v1.7) Saves the bootblock to a file ($400 bytes long).
You must type the file name between inserts for the target disk!
'F2' KEY:
°°°°°°°°°
(Update v1.7) Saves a virus that was in memory before loading the
MVK to a file.
UPDATE V2.0: Now you can select a drive or the HD before striking
------------ the F1 or F2 Keys. If you choose the HD, the message
"Right mouse button to continue" takes the place of "Insert a disk
in any drive".
V2.1: NEW 'T' KEY:
------------------
This Key is used to Display Number of MVK's reads and writes.
V2.1 RAM ICON:
--------------
Testing the memory takes time but is rather simple. The elimination of
whatever virus has, however, been painstakingly worked up:
Irrespective of the ROM version (1.2, 1.3...), how does one reinitialize
strategic vectors like BeginIO, DoIO etc...? For that I have programmed
a routine which searches in Rom for input-points that are used to find
good values again.
Uptdate v1.6 about this RAM Icon:
Instead of the hexadecimal read-out of the "exec.library", the ASCII text
equivalent of the ROM is displayed, which is easier to read. In addition,
the marker of the $68 interrupt is also displayed.
When I tested the Abraham Virus, I had the unpleasant surprise of seeing
this virus pass the memory test which should normally suppress it in memory.
The 1.5 version did not test the $68 interrupt. So, when I inserted a
diskette in whatever drive, the $68 interrupt awoke and so did the virus!
I proved this by cliking Ram Icon: the vectors were deviant again!
Holding the 'D' Key reveals the exact start address of the virus; this
allowed me to disassemble it quickly, because the virus in memory is
decripted.
Remarks v2.0: Now you can see more vectors. (I check more vectors too!)
------------- Please observe that the DoIO vector does not have a correct
ROM value when you check memory using the Ram Icon. This is so because MVK
uses the DoIO vector to check if a disk is present in any drive. Of course
when you exit this DoIO vector will be restored.
Remarks V2.1: Now DoIo vector is in Blue (and not red) when you click
------------- Ram Icon. I test many more vectors in this 2.1 version.
Because New RETURN OF LAMER EXTERMINATOR virus uses more vectors too..
Now when vectors are deviants this situation is reveals by a RED text
editing. Normal : White or Blue Color.
'D' KEY:
°°°°°°°°
To make a dump of the memory where the virus should be in theory, if one
is present during the memory test. I sweep this memory looking for the long
word "Dos,0"; then with the deviant vectors I can find in most cases the
correct start address of the virus. In fact, if a virus wants to be
reproduced on 'bootable' disks, it must entirely recopy its boot in memory.
All 'bootable' disks begin with the long word (4bytes) Dos,0.
After a check of deviant vectors I verify such vectors near this address
and if the boot has the mark of this "disk image" of a virus, it declares
itself as present in memory.
Obviously sometimes, the mark of a virus is present in memory, but no
vectors are deviant, i.e. such vectors are not active anymore. For this
reason the double test 'deviant vectors' and 'disk image' is necessary.
This testing does not take into account (like the memory test) the
'protector viruses' recognized by MVK. In fact these are not viruses.
(The series of PLV protectors is recognized by MVK when inserting a disk
in any drive, but they are not recognized for what they are with the memory
test which will undoubtedly report a dangerous or questionable bootblock.)
Update v1.8 about 'D' Key: Hexadecimal dump is now available.
Update v2.0: Does a test scanning memory for File Viruses.
------------ [Search HUNK_LOAD $000003E9] If boot virus, scans "DOS",0
'C' KEY:
°°°°°°°°
If you strike this key a window will be displayed. (You can push again the
F1, F2 or F3 Keys.) This is to control the Hard Disk device. Example:
xt.device to control A590 xt HD.
After pushing the key MVK loads the Boot of your HD and displays it.
Then you can see if you have damages. (I think this is for experts only!)
4.A few words about how to use MVK
///////////////////////////////////
Ver 2.1 update:
---------------
-First a line about "drive" HD:. Use it with "assign" as an "external"
drive or with TRACKsimulator (on an Amigalibdisk).
Type DH0: QDH0: DH1: FF1: etc... in the box when you click on the HD ICON.
-!!->Update v2.0: Starting MVK, if you click the left mouse button during
program loading you pass through the memory test. If you have problems with
the memory test (I'm thinking about the A3000) or with running the program,
quickly click the left mouse button again!
-If you discover new viruses or if you have incompatibility problems,
please use the VECTORS program (on this disk) and send me the results:
1>Vectors >prt:
or
1>Vectors >df1:File_for_XL
-The duplication icon: Simply use this icon to copy any boot from a drive
dfx: to another drive dfy:. The checksum is automatically recalculated.
-Select one of the drives by clicking on its icon. Drives which are not
present during startup are not selectable. The automatic choice of a drive
occurs only when you have decided to install a special boot or to kill a
virus on a disk in such drive.
-!!Update v2.0: The automatic choice of a drive occurs now for a number of
actions.
When you click on the "File Virus?" icon or strike the F1/F2 Keys, however,
select the desired drive in advance!
When you insert a disk in a drive the corresponding drive icon is selected
automatically.
Ver2.1: R.O.L.E ? Icon:
-----------------------
Click this Icon to switch between ROLE Detection (very dangerous return of
lamer exterminator [1848 bytes Disk-validator new generation of virus]) and
or LINK detection.
-The 'Display Boot' option allows scanning the boot by inserting a disk.
(In case of a SCA virus, for instance, the text SCA is seen in 'bright'.)
The option is a handy one in case MVK gives a 'bootblock unknown' message.
In such case MVK can not identify the boot. It may have a new virus, or it
is a game boot or any other legitimate special boot. Whatever, DO NOT ALTER
THE BOOT IN ANY WAY ON THE DISK PROPER. Back-up the disk first, and do your
experimenting on the back-up. Changing whatever legitimate special boot may
cause the disk to become useless by disabling essential loading instructions.
Thus pay attention, unless you have an irrepressible and incomprehensible
urge to 'play virus' yourself!
-The 'IRQ protector' option allows installation of a special boot which will
let believe the link virus IRQ TEAM (it attaches to the first executable
file it can find, usually the startup-sequence) that it is already present
in memory. So, the would-be intruder will be kept out.
-The 'Install VDC' option (Virus Detector Cleaner) will install a boot
that will detect a virus or any other resident program. In such case the
screen will become red and a 'LONG RESET' will keep undesirable intruders
out of memory. A blue screen means that nothing has been detected. You will
note that the VDC option is most efficient and the best option for HD users.
You may wish to insert it in the startup-sequence. In fact, it makes
superfluous the memory test that MVK can perform at start, because, at the
present time and to the best of my knowledge, no virus can pass it. I had
some trouble previously with the Termigator boot virus (which, by the way,
runs only under v1.2 rom). It uses interrupts which put it off memory during
booting, and thus the VDC (in boot) doesn't find a thing and lets it pass.
The present version of VDC, however, does detect it. The offensive code is
disabled after booting and then the VDC code will find the intruder,
performs the reset and that spells death to Termigator.
Please note that it is unwise to use the VDC boot or the VDC instruction
if you want to detect a virus at the start of MVK. VDC simply smothers any
virus and it is therefore far from surprising that MVK will have nothing to
report.
MVK's memory test is unique in its kind, allowing the detection and
suppression of all viruses at start, irrespective of your rom version.
This test takes practically one third of the program and, personally, I
find it a pity not to give MVK a chance.....
Some further explanation about VDC is required. If it is put into your
startup-sequence as first instruction, it may come under attack by link
viruses. To put your mind at rest: that will never happen if you ALWAYS run
your applications from your hard disk! If not, then BGS9, IRQ TEAM,
TERRORISTS and what not, will replace VDC by their own code and will try to
run the instruction again, letting you believe nothing has been modified.
Please note that the virus is present already before VDC is run. Presently
VDC detects such virus and will perform a reset to suppress it.
That results in an ENDLESS LOOP!
Say you decide to check the boot. You will find nothing. Use the 'Kill Virus'
option? With the hard disk as it is now, that has become impossible.
It is time for you to realize that you have a link virus problem.
You have to replace the now-infected startup-sequence by the original one
and to copy the true VDC instruction over the one that is now infected.
If you are in doubt about the nature of the virus, run MVK: it will tell you.
In that case, as said before, do not give a pre-emptive smothering
instruction. Give MVK the opportunity to identify the intruder. It will then
duely smother it.
-Update of VDC (v1.6): As already briefly touched upon in the foregoing,
VDC has been revised and corrected. The $68 interrupt is now tested and,
consequently, VDC now presents an insuperable barrier against viruses using
this interrupt: Termigator, GX.Team and Class Abraham. It remains possible
to save your RAD:, if present: simply press the left mouse button.
The screen will duly become red but the long reset is not effected!
This option may also serve the 'virus shooter'. You can let live the virus
for studying it, knowing full well that at any time it can be smothered
using the VDC instruction normally.
-Update of VDC (v1.7): Low memory tests improved (testing from $8 to $3C
and from $40 to $BC).
-Update v2.0: Some viruses use new vectors to stay in memory and cause
extensive damages. Example: AvailMem() is made deviant to -seemingly-
maintain the amount of free memory the user considers normal.
MVK now tests these vectors and so does VDC. (AvailMem, KicksumData, and
many more).
Note: Many viruses now use new exec functions:
-630(A6) -QuickMemCopy -624(A6) -CopyMem etc.... (with move.l $4.W,A6)
-The 'Kill Virus' option writes a classic boot block on the target disk in
the drive previously selected (making noises to symbolize the death of the
virus). You can use this option without hesitation in case of a boot virus
recognized by MVK. But if MVK signals 'Unknown boot' then be careful, as
explained above.
-To exit from the program, just click on the icon that looks like an
interrupter.
Update v1.7 to exit: A requester is displayed upon exiting MVK.
Click on "OK" to preserve the RAD:, if present.
----------------------------------------------------------------------------
WARNING: NEVER click "OK" if a virus has been detected at the start of MVK!
The virus could revive upon the next reset. In this case OR if you don't
have a RAD: YOU MUST CLICK on "CANCEL" !
----------------------------------------------------------------------------
5.During operations:
--------------------
If a virus is detected upon insertion of a disk, a siren will sound and
possibly a reproduction gauge is displayed (if it exists for the virus)
plus an image of a virus. You only have to kill the virus or to install a
special boot replacing the virusboot. You can scan your victim with the
"Display Boot" option. Any action will stop the siren.
If a special boot is recognized by MVK it will display what sort of boot it
is. An image of a raised thumb to signify "OK" is displayed.
In case of a virus or a special bootblock not being part of MVK's library
of bootblocks, an 'ATTENTION' panel is displayed and the 'Bootblock Unknown'
message is shown. There is no change should such boot be a dangerous virus.
I consider it sound practice to remain curious, so I recommend proceeding as
follows:
IMPORTANT:
----------
First you can always try to read a possible message which might be
displayed in 'bright' (i.e. in ASCII) by scanning the boot with the
'display boot' option (you may see for example: "Virus by byte bandit...")
But most "modern" viruses are cripted, i.e. they don't allow direct reading
of this kind of message...
No panic: MVK has more than one trick up its sleeve!
Second: run the uncertain diskette (boot it) then reset and finally run MVK.
It will effect a memory test at start. If there is a new virus, the 'OK no
virus in memory' thumb won't be displayed. You will see the 'Unknown virus',
'Virus Protector' or 'Prog. Resident in Memory' message. The strategic and
necessary markers for a virus are not equal to zero!
That is not all! The third thing to do is to run MVK (the virus is
suppressed automaticaly) and then to strike the 'D' Key. This allows giving
a confirmed diagnosis. With the help of a complex algorithm, MVK seeks
the place where the virus (or the virus protector) was located and will
display this place in ASCII accompanied by the address in memory!
Generally at this level, the virus is decripted in memory and messages are
displayed in 'bright'.
The final thing to do is, obviously, not to forget informing me about the new
virus so that I can put it into an update of Master Virus Killer!
6.Have you said Virus ?
-----------------------
An attempt at definition.
Virus: a small program in Assembler which recurs, either discretely (i.e.
without advertising itself to the user) or by deceiving him about its true
nature.
(Remember the case of the Pentagon Circle Virus Slayer: seemingly a virus
protector but actually a virus!)
It all began with rather innocuous bootblock viruses, easily detectable on
the bootblock (SCA), progressed to harmful brothers (sisters?) still
detectable in like manner (Diskdoctors), then to cripted nephews (nieces?).
Now there are also link viruses. They are like the viruses on PC's which
infiltrate executable files. On the Amiga line ,there is the IRQ Virus, but
it isn't dangerous anymore. It has been rendered ineffective with the
advent of system v1.3 rom.
If you still operate on system v1.2, MVK has a trick to give protection
against it. The special IRQ protector boot will make the virus inactive even
if it is on an executable file.
The principle is very simple: before becoming active the IRQ virus will
verify whether the OldOpenLibrary vector is in ROM, otherwise it will
deduct it isn't in memory and vice versa. You just make this vector deviant
to your advantage and there you are!
(For link viruses: see the applicable list B)
7.The reproduction gauge
------------------------
The most time consuming and hardest work in setting up the program was the
disassemblage of all viruses MVK could detect. However, it revealed, for the
viruses which have one, the reproduction gauge.
It indicates how many times the virus has already infected others disks.
Example: (C)rackright by Diskdoctors: 678. The result is indeed amazing
sometimes!
8.How dangerous are viruses?
----------------------------
Most viruses nowadays cause irremediable damage.
You may get a black screen and jammed system during the rendering of an
image with SCUPLT 4D. (GxTeam, Byte Bandit viruses...) Viruses may format
a sector of your disk, or occupy a sector (Lamer Exterminator).
Or, stupidly, the virus will install itself on your disk and put it beyond
use (most games use custom bootblocks which the virus will mindlessly
destroy).
In conclusion: take the matter of viruses seriously!
9.How to be protected?
----------------------
-Use MVK each time you have doubts about the virginity of your disk's
bootblock and/or executable files.
-Keep your disks write-protected if at all possible. Don't believe the
idiots who say that this is no good. There is but one possibility to effect
writing on a disk and that is to make it write-enabled.
Even changing the state of the WPRT signal of the drive (14th pin of DB-23
to ground or to 15 volts) will alter nothing. The Amiga will think (will it?)
that the disk is write-enabled, allowing writing to the disk, but in fact
NOTHING WILL BE WRITTEN!
The drive's HARDWARE has absolute priority even over the logic signals of the
Amiga.
10.English Texts
----------------
V2.1: The English texts of v2.0 have been touched up thanks to a sympathetic
user in The Netherlands.
11.About R.O.L.E:
-----------------
SOME WORDS in English [ sorry my bad English ]: This Virus (return of lamer
exterminator ) is very very special. It's the first to erase Disk-Validator
(sys:l) and put its code (1848 bytes) at this place. When you insert some
disk in ANY DRIVE WITHOUT BOOTING THE DISK and if a ROLE is on the disk
then this role is loading and takes place in MEMORY. Then role produces
some read-writes/errors , "clean" the disk etc... See the ROLE disassembling
in VirusROLE.ART of the "disk_Virus_informations_V1.0". [See 12.]
Of course MVK detects and kills role.
12. VERY VERY IMPORTANT MESSAGE:
--------------------------------
To know more about Amiga Viruses you can "buy" (it's a Public Domain)
the "Disk_Virus_Informations_V1.0". The contains of this disk is about
200Kbytes files texts about Viruses. Quick Sort contents:
VIRUS_INFORMATIONS_V1.0 (dir)
!!FLEAUX.DOC!! !!FLEAUX.DOC!!.info
.info Abraham.ART
Abraham.ART.info Alimentation.ART
Alimentation.ART.info BSG9_NEWS
BSG9_NEWS.info ByteBandit.S
ByteBandit.S.info ByteWarrior.S
ByteWarrior.S.info Extreme.S
Extreme.S.info Gadaffi.S
HCS.S HCS.S.info
MVK_FR.DOC MVK_FR.DOC.info
RSI.ART RSI.ART.info
TASK.ART TASK.ART.info
VirusROLE.ART VirusROLE.ART.info
Where? FREE DISTRIBUTION P.O.BOX 134 , 59453 Lys Lez Lannoy Cedex FRANCE.
Good use of the Master Virus Killer! See you for my next version. (v2.2)
Please ,please ,please if you own new viruses SEND IT TO ME !!!!!
Thanx !!!!!!!!!!!!!!!
X.L MARS/AVRIL 1991